jest-message-util

What is jest-message-util?

The jest-message-util package provides utilities for formatting and handling error messages in Jest, a popular JavaScript testing framework. It is particularly useful for creating custom error messages and enhancing the readability of test results.

What are jest-message-util's main functionalities?

formatStackTrace

The formatStackTrace function formats a stack trace to make it more readable. This is particularly useful for debugging and understanding where errors occur in your tests.

const { formatStackTrace } = require('jest-message-util');
const stack = new Error().stack;
const formattedStack = formatStackTrace(stack, { rootDir: process.cwd(), testMatch: [] });
console.log(formattedStack);

formatExecError

The formatExecError function formats execution errors to provide more context and readability. This helps in quickly identifying the cause of test failures.

const { formatExecError } = require('jest-message-util');
const error = new Error('Test error');
const formattedError = formatExecError(error, { rootDir: process.cwd(), testMatch: [] });
console.log(formattedError);

getTopFrame

The getTopFrame function extracts the top frame from a stack trace. This is useful for pinpointing the exact location of an error in your code.

const { getTopFrame } = require('jest-message-util');
const stack = new Error().stack;
const topFrame = getTopFrame(stack);
console.log(topFrame);

Other packages similar to jest-message-util

stack-utils

The stack-utils package provides utilities for working with stack traces. It offers similar functionality to jest-message-util, such as formatting and parsing stack traces, but is more general-purpose and not specifically tailored for Jest.

error-stack-parser

The error-stack-parser package is designed to parse and extract information from error stack traces. While it offers similar capabilities to jest-message-util in terms of stack trace manipulation, it does not provide the same level of integration with Jest.

pretty-error

The pretty-error package focuses on making error messages more readable by formatting them in a visually appealing way. It offers similar functionality to jest-message-util's formatting features but is more focused on aesthetics and less on integration with testing frameworks.

README

The README file is missing

Changelog

26.6.2

Features

• [jest-core] Add findRelatedTests and nonFlagArgs in allowed config options for updateConfigAndRun in watch plugins (#10659)

Fixes

• [babel-plugin-jest-hoist] Preserve order of hoisted mock nodes within containing block (#10536)
• [babel-plugin-jest-hoist] Hoist pure constants to support experimental JSX transform in hoisted mocks (#10723)
• [babel-preset-jest] Update babel-preset-current-node-syntax to support top level await (#10747)
• [expect] Revert "Fix objectContaining to work recursively into sub-objects (#10508)" (#10766)
• [jest-circus, jest-jasmine2] fix: don't assume stack is always a string (#10697)
• [jest-config] Fix bug introduced in watch mode by PR #10678 (#10692)
• [jest-config] Throw correct error for missing preset modules (#10737)
• [jest-resolve-dependencies] Resolve mocks as dependencies (#10713)
• [jest-runtime] Handle file URLs in dynamic imports (#10744)
• [jest-runtime, babel-jest] Pass more ESM options to @jest/transform (#10752)
• [jest-runtime] Properly inject extraGlobals into the runtime (#10758)
• [jest-transform] Link to ESM docs on syntax errors (#10748)

Chore & Maintenance

• [docs] Add docs for using mocks in TypeScript (#10415)
• [eslint-config-fb-strict] Move package from this repo to fbjs repo (#10739)
• [examples] Update TypeScript example to show use of newer Jest types (#10399)
• [jest-cli] chore: standardize files and folder names (#10698)
• [jest-config] Switch ts-node Register type to Service due to deprecation (#11210)